|
|
 |
|
Poster:
|
 molly |
Date:
|
April 08, 2005 05:51:03am |
|
Forum:
|
texts
|
Subject:
|
Re: Reading Error Reports on Texts |
We are designing a new error reporting system specifically for texts that will become part of the metadata. Some of the books in our archive cannot be fixed by us, since we didn't scan the book in the first place. However, if some other scanning project happens to have scanned the page, we want to make it so that they can donate just the missing page.
In order for this to happen, we need to create a public error reporting system for texts, and rank it by book, scan, and processing error. For example, a missing page could be a physically missing in the book, a page that was in the book that didn't get scanned, or a page dropped while it was processed.
Anyhow, that's on our big ToDo list for how to make our text collection better. For now when we get a reported error in texts that we can't do anything about, we are sticking it in the description feild. We need to go through the old error reports and close them out and make them public.
Please don't feel like your efforts are going unnoticed! They are much appreciated.
-best
Molly
|
Poster:
|
papeters |
Date:
|
April 10, 2005 03:47:07pm |
|
Forum:
|
texts
|
Subject:
|
Re: Reading Error Reports on Texts |
Thank you for your considerate reply.
"In order for this to happen, we need to create a public error reporting system for texts, and rank it by book, scan, and processing error. For example, a missing page could be a physically missing in the book, a page that was in the book that didn't get scanned, or a page dropped while it was processed."
I agree this is a thorough solution.
Could you please consider a prototype mechanism in the interim?
One that allows us to create error metadata records that indicate the book and whether the problem is with other metadate (title, publication date, etc.) or with a page (identify book page number or tif file number ... or "many/multiple" for books that have lots of problems). That and either a pick-list or free-form description of the problem should all be usable in your final solution and would allow us to make progress on tracking need & supplying replacement/additional scans in the meantime. The old format error reports will largely fit in this scheme, with minor manual intervention to extract page numbers from the error report's text.
I understand the long-term need to know the underlying cause for errors so processes can be improved. I hate to see nothing available while the grand solution is pending in a to-do list.
|
Poster:
|
papeters |
Date:
|
April 10, 2005 03:59:02pm |
|
Forum:
|
texts
|
Subject:
|
Re: Reading Error Reports on Texts |
p.s. I have to wonder how the creation of a new system is helped by the current state of things. I still create new error reports in the old format; I just can see the history any more. If it was truly a conversion issue, I would have expected a really different error *reporting* page.
|
Poster:
|
tonyfirshman |
Date:
|
May 04, 2009 11:41:54am |
|
Forum:
|
texts
|
Subject:
|
Re: Reading Error Reports on Texts |
Did this project get off the ground?
There is a scanning error (or missing pages) on
http://www.archive.org/details/historyofphilhar00fostBetween scanned pages 21 and 22, there should be the book's pages 3 and 4.
TVNews
OpenLibrary